Skip to content

Conversation

@jihoonsong
Copy link
Contributor

This PR clarifies the SignedExecutionPayloadEnvelope construction section.

Comment on lines -235 to -239
After setting these parameters, the builder assembles
`signed_execution_payload_envelope = SignedExecutionPayloadEnvelope(message=envelope, signature=BLSSignature())`,
then verify that the envelope is valid with
`process_execution_payload(state, signed_execution_payload_envelope, execution_engine, verify=False)`.
This function should not trigger an exception.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm I'm pretty sure this section is necessary. I believe we want builders to check that the execution payload envelope is valid before setting envelope.state_root. If this is not the case, we can/should remove the verify parameter entirely.

cc @potuz

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, isn't it at L248? I thought it's a duplicate and just wanted to make a stylistic change without changing original meaning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants